Systems and methods for authenticating photographic image data

ABSTRACT

The present disclosure provides systems and methods for authenticating photographic data. In one embodiment, a method comprises providing an image authentication application for use on a client device, the application configured to control image capture and transmission; receiving an image data file from the application at the authentication server comprising a photographic image captured by the application and metadata associated therewith; applying a watermark to the photographic image to create a watermarked image; applying date and time information to the tagged image; applying location information to the tagged image; creating a web address associated with the image data file; uploading the photographic image, the tagged image, or both to the web address; and transmitting an authenticated image file to the client device, the authenticated image file comprising one or more of: the watermarked image, the photographic image, the date and time information, geographic information, and the web address.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/909,335, filed Jun. 23, 2020, which is a continuation of U.S. patentapplication Ser. No. 16/114,428, filed Aug. 28, 2018 (which issued asU.S. Pat. No. 10,733,315 on Aug. 4, 2020), which is a continuation ofU.S. patent application Ser. No. 15/065,781, filed Mar. 9, 2016 (whichissued as U.S. Pat. No. 10,095,877 on Oct. 9, 2018), which is acontinuation of U.S. patent application Ser. No. 14/816,712, filed Aug.3, 2015 (which issued as U.S. Pat. No. 9,300,678 on Mar. 29, 2016), theentireties of which are incorporated by reference herein.

TECHNICAL FIELD

The present disclosure relates to systems and methods for authenticatingphotographic image data, including a software application forcontrolling photography on a client device and metadata associatedtherewith and an authentication server for receiving data therefrom.

BACKGROUND OF THE INVENTION

Digital photography has grown steadily since its introduction. Socialnetworks and mobile computing devices have further accelerated thegrowth of photographic data made available to the public. The ability totake and share photographs anytime and anywhere has resulted in thegeneral public consuming more photographic data than ever and relying onthese photographs for up to the minute information. However, it is awell-known fact that digital photographs are easily edited and theinformation contained within a digital photograph may not be entirelytrustworthy.

SUMMARY OF THE INVENTION

One aspect of the invention relates to a software application thatresides on a client device (e.g., a smart phone or other client device)for controlling various aspects of photography on the client devicewhere authentication of photos is desired, an authentication server forreceiving a photo and associated data therefrom and creating anauthenticated photo and a website for storing the authenticated photosand which enables users who subsequently receive a copy of the photo todetermine if it is an authentic photo. Collectively, the imageauthentication application and authentication server are configured tobe operable to control the taking of photos to be authenticated and theassociation of metadata with those photos. The image authenticationapplication may require users, desiring to generate an authenticatedphoto, to invoke the image authentication application to take a picture.The image authentication application and authentication server includefunctionality to reduce the likelihood of alteration of metadataassociated with a picture taken under control of the application.

Once a picture is taken under control of the image authenticationapplication, it is sent from the image authentication application to theauthentication server. The image authentication application may preventa photo that has been taken from being edited or sent from the imageauthentication application to any location other than the authenticationserver. This helps prevent alteration of the photo.

The image authentication application (in conjunction with theauthentication server) may also facilitate the authenticity of metadataassociated with the photo.

According to one aspect, the image authentication application mayrequire a user to grant access to the device's geolocation data whenopening the app for the first time (and/or at other times). The imageauthentication application may track the device's position as long asthe app is active using geolocation capabilities on the client device.This helps prevent and/or enables detection of alterations to thelocation metadata.

To take a picture the user may be required to open the imageauthentication application (if it is not already open on the device).After taking a picture using the image authentication application andselecting to use the photo, the image will be transmitted to theauthentication server along with various metadata, such as geographicinformation, e.g., the user's current latitude/longitude, time data ifdesired and/or other metadata.

According to one aspect, the time at which the image is received by theserver is recorded. This helps prevent alteration of the time metadataassociated with the photo. In various prior approaches to photoauthentication, the time data is generated solely by the client device.A problem with these prior approaches is that users can alter the systemtime of the client device.

The user's latitude/longitude may be used to determine address andnearby places of interests. If places of interest are found, the userwill be prompted to tag their image with that location name. Users willalso be given the option of removing the address/location informationall together. However, the application may prevent users from adding ormodifying location information.

In certain embodiments, the application may include a feature to ensurethat the time delay between opening the application and/or taking aphoto in the image authentication application and sending the image tothe authentication server is within an approved time frame. Similarly,the image authentication application may include a feature to ensurethat the location at which a photograph was taken is within an approveddistance limitation from the location from which the user transmits thephotograph to the authentication server.

According to another aspect, the authentication server performs varioussteps to facilitate authentication of photos received from theapplication. When a photo is received, the authentication server mayassign it a unique resource locator (e.g., a unique web address). Theauthenticated image (or a version of the authenticated image), andassociated metadata, is stored on the authentication server. The uniqueresource locator (e.g., a web address or a web address proxy such as abitly code or a tinyURL) may be provided along with the authenticatedimage for third party verification of the image. The website (and/orother distribution infrastructure) will allow third parties to check andreference the authenticated image to verify that it is authentic. Theauthentication server may host and/or be in communication with thewebsite. Any third party can visit the authentication server website tolook up the authenticated image they have been provided and to make surethat the picture they are viewing is also on the website. This insuresthat the image provided to the third party viewer has, in fact, beenauthenticated by the authentication server.

The features disclosed herein may be applied to videos as well asimages.

In certain embodiments, a block chain server system may be implementedsuch that multiple authentication servers store and maintainauthenticated image information.

The present disclosure may be embodied in a method comprising providingan image authentication application for use on a client device, theimage authentication application configured to control image capture andimage transmission by the client device; receiving an image data filefrom the image authentication application at an authentication server,the image data file comprising a photographic image captured by theimage authentication application on the client device and metadataassociated with the photographic image; applying an authenticationindicator to the photographic image to create a tagged image at theauthentication server; applying date and time information to the taggedimage at the authentication server; creating a resource locationidentifier associated with the image data file, the resource locationidentifier identifying a file location; uploading the photographicimage, the tagged image, or both to the file location identified by theresource location identifier; and transmitting an authenticated imagefile to the client device, the authenticated image file comprising oneor more of: the tagged image, the photographic image, the date and timeinformation, and the resource location identifier.

In one aspect of this embodiment, the method may further comprise usingthe metadata to verify that the image data file has satisfied one ormore timing requirements. The one or more timing requirements maycomprise a requirement that the image data file was received at theauthentication server within a predetermined time frame after thephotographic image was captured by the image authentication application.Alternatively, or in addition, the one or more timing requirements maycomprise a requirement that the image data file was received at theauthentication server within a predetermined time frame after the imageauthentication application was opened on the client device.

In another aspect of this embodiment, receipt of the image data filefrom the application indicates that the image authentication applicationhas verified that the image data file has satisfied one or more timingrequirements. The one or more timing requirements may comprise arequirement that the image authentication application received a requestto transmit the image data file to the authentication server within apredetermined time frame after the photographic image was captured bythe image authentication application. Alternatively, or in addition, theone or more timing requirements may comprise a requirement that theauthentication application received a request to transmit the image datafile to the authentication server within a predetermined time frameafter the image authentication application was opened on the clientdevice.

In another aspect of this embodiment, the authenticity indicator maycomprise a visual watermark applied to the photographic image.

The present disclosure may also be embodied in a method comprisingopening an image authentication application on a client device;capturing a photographic image using the image authenticationapplication; transmitting the photographic image to an authenticationserver using the image authentication application; receiving anauthenticated image file on the client device from the authenticationserver; and sharing the authenticated image file. The authenticatedimage file may comprise an authenticated image that has beenauthenticated by the authentication server; authenticated date and timeinformation provided by the authentication server and associated withthe authenticated image; and a resource location identifier associatedwith the authenticated image identifying a file location, wherein athird party viewer may visit the file location to view the photographicimage, the authenticated image, or both.

In one aspect of this embodiment, the image authentication applicationmay prevent editing of the photographic image, and exporting of thephotographic image except to the authentication server.

In another aspect of this embodiment, the authenticated image maycomprise a watermark indicating that the authenticated photo has beenauthenticated by the authentication server.

In another aspect of this embodiment, the method may further compriserecording time information corresponding to when the imageauthentication application was opened on the client device; and beforetransmission of the photographic image to the authentication server,confirming that transmission of the photographic image to theauthentication server is occurring within a predetermined time frameafter the image authentication application was opened on the clientdevice.

In another aspect of this embodiment, the method may further compriserecording time information corresponding to when the photographic imagewas captured using the image authentication application; and beforetransmission of the photographic image to the authentication server,confirming that transmission of the photographic image to theauthentication server is occurring within a predetermined time frameafter the photographic image was captured using the image authenticationapplication.

The present disclosure may also be embodied in a photographic dataauthentication system, the system comprising a client device having animage authentication application; and an authentication server incommunication with the client device over a wide area network. The imageauthentication application on the client device may be configured tocapture a photographic image, receive a command to transmit thephotographic image to the authentication server, determine whether thecommand to transmit the photographic image to the authentication serversatisfies one or more time or geographic restrictions, and if the one ormore time or geographic restrictions are satisfied, transmit thephotographic image to the authentication server for authentication. Theauthentication server may be configured to apply authenticated time anddate information to the photographic image, apply an authenticationindicator to the photographic image to create an tagged image, create aresource location identifier associated with the authenticated image,the resource location identifier specifying a file location, andtransmit an authenticated image file to the client device. Theauthenticated image file may comprise the tagged image, theauthenticated time and date information, and the resource locationidentifier.

In one aspect of this embodiment, the one or more time or geographicrestrictions may comprise a restriction that the image authenticationapplication must receive a request to transmit the photographic image tothe authentication server within a predetermined time frame after theimage authentication application is opened on the client device.

In another aspect of this embodiment, the one or more time or geographicrestrictions may comprise a restriction that the image authenticationapplication must receive a request to transmit the photographic image tothe authentication server within a predetermined time frame after thephotographic image has been captured by the image authenticationapplication.

The present disclosure may also be embodied in a method comprising:receiving a watermarked image, the watermarked image comprising aphotographic image and a watermark indicating that the photographicimage has been authenticated by an authentication server; receiving aweb address associated with the watermarked image, the web addressdisplaying the watermarked image, the photographic image, or both; andvisiting the web address to verify the authenticity of the watermarkedimage.

In one aspect of this embodiment, receiving the web address may comprisereceiving a shortened representation of the web address, and/or a QRcode representation of a web address.

In another aspect of this embodiment, the method may further comprisereceiving authenticated metadata associated with the watermarked image,and visiting the web address to verify the authenticated metadata.

The present disclosure may also be embodied in non-transitory computerreadable medium comprising an instruction set configured to command acomputing device to carry out the methods described herein.

These and other features and advantages of the invention should becomemore readily apparent from the detailed description of the preferredembodiments set forth below taken in conjunction with the accompanyingdrawings, which illustrate, by way of example, the principles of thedisclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings are provided for purposes of illustration only and merelydepict typical or example implementations. These drawings are providedto facilitate the reader's understanding and shall not be consideredlimiting of the breadth, scope, or applicability of the disclosure. Forclarity and ease of illustration, these drawings are not necessarilydrawn to scale.

FIG. 1 provides a perspective view of a photographic image dataauthentication system, in accordance with an embodiment of the presentdisclosure.

FIG. 2 provides a block diagram representation of a client device havingan image authentication application, in accordance with an embodiment ofthe present disclosure.

FIG. 3 provides a flow-chart depiction of a photographic image dataauthentication process from the perspective of a client device, inaccordance with an embodiment of the present disclosure.

FIG. 4 provides a flow-chart depiction of a photographic image dataauthentication process from the perspective of a photographic image dataauthentication server, in accordance with an embodiment of the presentdisclosure.

FIG. 5 provides a flow-chart depiction of a photographic image dataauthentication process from the perspective of a third-party recipientof an authenticated image, in accordance with an embodiment of thepresent disclosure.

FIG. 6 illustrates a sample computing module that may be used toimplement certain features and embodiments of the present disclosure.

DETAILED DESCRIPTION

The present disclosure provides systems and methods for authenticatingphotographic image data. One advantage of the disclosed systems andmethods is that users are able to authenticate photographic image dataso that the user can have some level of assurance that the informationcontained within a photographic image is accurate.

Referring now to the figures, FIG. 1 provides a block diagram of aphotographic image data authentication system 10. The system 10comprises a client device 12, an authentication server 14, and a network16. The client device 12 includes a camera capable of taking digitalimages and/or videos, and an image authentication application resides onthe client device 12 for controlling various aspects of photography onthe client device where authentication of photographic images isdesired. In FIG. 1, the client device 12 is shown as a mobile devicehaving a camera. However, it should be understood that the client device12 may be any device capable of taking digital photographic images,including, but not limited to, cell phones, smart phones, tablets, othermobile devices, digital cameras, web cameras, laptop computers, desktopcomputers, security cameras, televisions, monitors, and the like. Theclient device 12 is connected to the authentication server 14 over thenetwork 16. In certain embodiments, the network 16 may be a wide areanetwork, such as the Internet.

When a user wishes to take an authenticated image, the user opens theimage authentication application on the client device 12 to capture animage. Once the user captures an image using the image authenticationapplication on the client device 12, the image along with any associatedmetadata (collectively referred to as the “image file”) is transmittedover the network 16 to the authentication server 14 for authentication.The authentication server performs various tasks to authenticate theimage file, thereby providing third-parties some level of assurance thatthe authenticated image file is unaltered and reliable. Metadataassociated with an image may include a time-stamp (i.e., what time thephotograph was taken), a date-stamp (i.e., the date on which thephotograph was taken), and geographic information (i.e., the location inwhich the photograph was taken). Once the image file is verified andauthenticated by the authentication server, a watermarked image andauthenticated metadata (collectively referred to as the “authenticatedimage file”) are transmitted back to the client device. Theauthenticated image file may be shared with third-party viewers (e.g.,remote user 20 and social media network 22). The authenticated imagefile may also be uploaded to a website 18 hosted by the authenticationserver 14 for further verification of the authenticated image file.Third-party viewers who have received the authenticated image file canvisit the website 18 to confirm that the authenticated image file hasbeen verified by the authentication server and has not been changed inany way. In certain embodiments, rather than authentication occurring ata single server 14, a block chain server arrangement may be utilized sothat authentication may occur at numerous servers 24 located in variouslocations on the network 16.

FIG. 2 provides a block diagram of an exemplary client device 12. Theclient device 12 comprises a camera 40 that is controlled by a camerafunction 52. The client device 12 also comprises a geolocation function54 for tracking the location of the client device 12 and a clockfunction 56 for keeping track of time. Residing on the client device 12are an image authentication application 50 and a native cameraapplication 60. The native camera application 60 may be used to captureimages that a user wishes to edit and/or do not need authentication. Theimage authentication application 50 may be used when a user wishes tocapture and share authenticated images. The image authenticationapplication 50 is given access to the camera function 52 (to captureimages), the geolocation function 54 (for creating geographic metadataassociated with images), and the clock function 56 (for creatingtime-based metadata associated with images). A user can use the imageauthentication application 50 to capture an image (72), transmit theimage to the authentication server (74), and share an authenticatedimage (76). These functions are described in greater detail below.

It should readily be appreciated that authenticated images can bebeneficial and useful in many different applications. By way of example,authenticated images can be used by dating websites, social networks,casting directors, and the like to ensure accurate and recent images ofusers. Parents may use authenticated images to verify the whereaboutsand activities of their children or employers the whereabouts of theiremployees. Social media users can share experiences and users can viewfriends' images with full faith that the image is an accuraterepresentation of their activities. Delivery services can providereliable package tracking and location information. Customers makingonline purchases or reservations can verify the condition of the itemthey are purchasing or the item/property/vehicle they are renting. Newsoutlets can verify source image information. Witnesses to a crime oraccident can provide reliable, verifiable images taken at the scene.These are but a few of the myriad of uses that are possible withauthenticated images.

Although a broad overview of the systems and methods have been providedin describing FIGS. 1 and 2, various aspects of the authenticationprocess are described in greater detail below with reference to FIGS. 3,4, and 5.

FIGS. 3, 4, and 5 provide method flow charts for carrying out certainembodiments of photographic image authentication processes from theperspective of the client device 12, the authentication server 14, andthird party viewers, respectively.

FIG. 3 provides a flow chart depiction of an image authenticationprocess from the perspective of the client device 12. As stated above,an image authentication application resides on the client device 12 fortaking, authenticating, and sharing photographic images. At block 105,the image authentication application is opened on the client device.When it is opened, the image authentication application may record thetime that the image authentication application is opened, and thegeographic location of the client device at the time the imageauthentication application is opened (block 110). This information maybe used in later steps to ensure that the photograph has not beenedited. A user then captures an image using the application (block 115).Again, the time that the image is captured and/or the geographiclocation of the client device at the time the image was captured may berecorded (block 120). The time and location information recorded inblocks 110 and 120 may be associated with and/or applied to the image asmetadata. The time and location metadata and any other metadataassociated with the image may be grouped together into an image file.The image authentication application then receives a request from theuser to transmit the image file to the application server (block 125).In certain embodiments, this “request” may be an indication by the userthat the user wishes to authenticate the image file or to use the imageas an authenticated image.

When a user indicates a desire to authenticate the image file, the imageauthentication application may take one or more steps to confirm thatthe user has not had the opportunity to edit the image file by ensuringthat certain time and/or geographic restrictions are satisfied (block130). For example, the image authentication application may note thetime at which the image authentication application was opened (fromblock 110), and the time at which the request to transmit the image fileis made (block 125). If the request to transmit the image file is madesufficiently soon after the image authentication application is opened(for example, within one minute), then one can be fairly certain thatthe user has not had a chance to edit the image file in that short time.In certain embodiments, the image authentication application may alsocompare the geographic location of the client device at the time theimage authentication application was opened (from block 110) and thegeographic location of the client device at the time the user requeststransmission of the image to the authentication server (block 125) toensure that the user has not moved a great distance (e.g., less than 200feet). Similarly, time and/or geographic information recorded when theimage was captured (from block 120) may be used and compared to timeand/or geographic information when the request to transmit the imagefile is made (block 125). These time and geographic requirements help toensure that the user has not had sufficient time to edit the image file.

Additional restrictions may be placed by the image authenticationapplication to assist in this authentication process. For example, theimage authentication application may only allow images taken within theimage authentication application to be transmitted to the authenticationserver. The image authentication application may also prohibit the useof any editing tools within the image authentication application, or toprohibit exporting of images so that the user cannot export images toanother program for editing. In this way, the image authenticationapplication ensures that the image file has remained within the approvedapplication environment for the entirety of the image file's existence,and that the user has not been given the opportunity to revise anyportion of the image file, including the image itself or the associatedmetadata.

Once the image authentication application has confirmed that the imagefile satisfies any time or geographic restrictions, the image file istransmitted from the image authentication application to theauthentication server (block 135). For example, as discussed above, theimage file may include the image itself as well as the geographiccoordinates at the time the photograph was taken and/or at the time theapplication was opened and/or at the time the transmission request wasmade may be transmitted to the authentication server (i.e., geographicmetadata). In certain embodiments, the time and date informationrecorded at any of the aforementioned events may also be transmitted tothe authentication server (i.e., time metadata). Once the authenticationserver has gone through its processes (described below in FIG. 4), theclient device receives a watermarked image and authenticated metadata(collectively, the authenticated image file) from the authenticationserver (block 140). As will be described in greater detail below, theauthenticated image file may include authenticated metadata provided bythe authentication server, such as a server-applied time stamp, datestamp, and geographic information. The authenticated image file may alsoinclude a resource location identifier associated with the authenticatedimage file. In certain embodiments, this resource location identifiermay be a web address or a representation of a web address (e.g., bitlycode, tinyURL, or QR code). In this scenario, the authenticated imagefile, or certain portions of the authenticated image file may beuploaded to a website viewable by third parties. The user can share theauthenticated image file with third party viewers (block 145) torepresent that the image being shared has not been edited or revised.Third party viewers can view the authenticated image file and access theweb address to confirm that the image has been verified by theauthentication server and has not been revised.

In certain embodiments, the authenticated image file may comprise anycombination of an authenticated image (i.e., the original image once ithas been verified by the authentication server), authenticated imagemetadata (e.g., authentication server-provided or authenticationserver-approved timestamp, datestamp, and geographic data), and/or awatermarked image, the watermarked image being the authenticated imagewith a visual watermark affixed to it to represent that it has beenverified by the authentication server.

Turning now to FIG. 4, the photographic image data authenticationprocess is described from the perspective of the authentication server14. In block 205, the authentication server 14 receives a photographicimage file (i.e., image and metadata) from the image authenticationapplication. For example, as discussed above, the authentication servermay receive time information (e.g., time/date when application wasopened, time/date when photograph was taken, and/or time/dateapplication received request to transmit photograph to authenticationserver), and/or geographic information (e.g., coordinates whenapplication was opened, coordinates when photograph was taken, and/orcoordinates when application received request to transmit photograph toauthentication server). As discussed above with reference to block 130of FIG. 3, the process confirms that certain time and/or geographicrestrictions are satisfied by the image file. As discussed above, byensuring that the user has not had an opportunity to edit the photograph(e.g., by ensuring that less than a minute has passed since the usertook the photo and transmitted it to the authentication server), theauthenticity of the photo can be presumed with reasonable certainty.Once it is confirmed that these restrictions are satisfied and the imagefile is received by the authentication server, the photographic image(part of the photographic image file) becomes an authenticated image.While FIGS. 3 and 4 depict that the client device determines whether ornot the time/geographic restrictions are satisfied, it is possible thatthis determination can be performed by the client device, theauthentication server, or both. In block 205 of FIG. 4, the photographicimage has satisfied the time and geographic restrictions and has beenreceived by the authentication server. As such, the image has beenauthenticated.

In block 210, the authentication server applies an authenticationindicator to the authenticated image. The authentication indicator maybe any indicator that the image has been authenticated by theauthentication server. A common example that was discussed above isapplying a watermark to the authenticated image to create a watermarkedimage. Although the example of a watermarked image is used throughoutthis disclosure as an exemplary embodiment, it should be understood thatinstead of a watermark, any other authentication indicator may be used(e.g., a metadata tag indicating authentication, or other visual and/oraudio indicators).

In block 215, authenticated metadata is then applied to theauthenticated image, the watermarked image, or both. This authenticatedmetadata may comprise time metadata and/or geographic metadata providedby or verified by the authentication server. For example, theauthenticated metadata applied to the authenticated image and/or thewatermarked image may comprise a time and date stamp provided by theauthentication server. The authentication server applies the time anddate stamp so as to avoid the possibility that the user has tamperedwith time and date settings on the client device. The authenticationserver may use a reliable time and date reading independent of theclient device and outside the reach of the user to tag the authenticatedimage with authenticated time and date information. The time and dateapplied to the authenticated image may be the time and date that theauthentication server received the original photograph.

The authenticated metadata may also comprise a geographic component. Inblock 205, the authentication server received metadata associated withthe photographic image as part of the photographic image file. Thismetadata may include geographic information (e.g., where the image wascaptured). The authentication server may use the geographic information(e.g., coordinates) in various ways. For example, the imageauthentication application may request the user to indicate the locationthe photograph was taken (e.g., an address or name of location), andtransmit that information along with application-recorded coordinateinformation to the authentication server as part of the photographicimage file. The authentication server may then compare the recordedcoordinate information with the address/point of interest informationprovided by the user to insure that the user has provided accurategeographic information. Alternatively, the authentication server maytake coordinate information provided by the image authenticationapplication to search for a corresponding address or nearby points ofinterest, and suggest these addresses/points of interest to the user.The user may be given the option to include geographic information withthe authenticated image file or remove it, but is prohibited frommodifying location information or adding unverifiable locationinformation.

The authentication server also creates a resource location identifierassociated with the authenticated image and/or the watermarked image sothat third party viewers can visit the URL and confirm that the imagehas been authenticated. The resource location identified may be a webaddress or a shortened web address to direct a third party viewer to awebpage where they can view the authenticated image and/or thewatermarked image. A copy of the authenticated image and/or thewatermarked image can be uploaded to the web address so that third partyviewers can view the authenticated image and/or compare an image theyhave received with the authenticated image at the web address. Finally,the authenticated image file, which may comprise any combination of theauthenticated image, the watermarked image, and/or the authenticatedmetadata, is transmitted to the client device (block 225).

Finally, FIG. 5 provides a photographic image data authentication methodfrom the perspective of a third party viewer. The third party viewer mayreceive an allegedly authenticated photograph from a user of thephotographic data authentication system (block 305). The photograph mayinclude a watermark that indicates that the photograph has beenauthenticated. However, it is possible that the user has falsely appliedthe watermark to an unauthenticated and/or edited image. To confirm thatthe image has, in fact, been authenticated and has not been edited inany way, the third party viewer may visit the web address associatedwith the watermarked image (block 310). The web address may appear onthe watermarked image itself (for example, may be part of thewatermark), or may be provided by the sender of the image, or may beembedded in the image such that clicking on the watermarked image willlead the user directly to the web address. In certain embodiments, theweb address may be the full address, or a representation of the address(e.g., a QR code, or a tinyURL, or a bitly address). By visiting the webaddress, the third party viewer can verify that the allegedlyauthenticated photograph has, in fact, been authenticated.

Although the figures and examples discussed above were discussed withrespect to photographic images, it should be understood that the systemsand processes disclosed above may be used in conjunction with videosrather than still images. Further, as discussed above, authentication ofimages or videos may be performed by multiple authentication serversrather than a single authentication server.

It should be understood that while the figures have presented exemplaryembodiments of the present systems and methods, revisions may be made tothe disclosed systems and methods without departing from the scope ofthe present disclosure.

Where components or modules of the disclosed systems and methods areimplemented in whole or in part using software, in one embodiment, thesesoftware elements can be implemented to operate with a computing orprocessing module capable of carrying out the functionality describedwith respect thereto. After reading this description, it will becomeapparent to a person skilled in the relevant art how to implement thedisclosure using other computing modules or architectures.

As used herein, the term module might describe a given unit offunctionality that can be performed in accordance with one or moreimplementations. As used herein, a module might be implemented utilizingany form of hardware, software, or a combination thereof. For example,one or more processors, controllers, ASICs, PLAs, PALs, CPLDs, FPGAs,logical components, software routines or other mechanisms might beimplemented to make up a module. In implementation, the various modulesdescribed herein might be implemented as discrete modules or thefunctions and features described can be shared in part or in total amongone or more modules. In other words, as would be apparent to one ofordinary skill in the art after reading this description, the variousfeatures and functionality described herein may be implemented in anygiven application and can be implemented in one or more separate orshared modules in various combinations and permutations. Even thoughvarious features or elements of functionality may be individuallydescribed or claimed as separate modules, one of ordinary skill in theart will understand that these features and functionality can be sharedamong one or more common software and hardware elements, and suchdescription shall not require or imply that separate hardware orsoftware components are used to implement such features orfunctionality.

Referring now to FIG. 5, computing module 400 may represent, forexample, computing or processing capabilities found within desktop,laptop and notebook computers; hand-held computing devices (PDA's, smartphones, cell phones, palmtops, tablets, etc.); or any other type ofspecial-purpose or general-purpose computing devices as may beappropriate. Computing module 400 might also represent computingcapabilities embedded within or otherwise available to a given device.For example, a computing module might be found in other electronicdevices such as, for example, digital cameras, portable media players,televisions/home theaters, in-car entertainment systems, video gameconsoles, video download or streaming devices, and other electronicdevices that might include some form of processing capability.

Computing module 400 might include, for example, one or more processors,controllers, control modules, or other processing devices, such as aprocessor 404. Processor 404 might be implemented using ageneral-purpose or special-purpose processing engine such as, forexample, a microprocessor, controller, or other control logic. In theillustrated example, processor 404 is connected to a bus 402, althoughany communication medium can be used to facilitate interaction withother components of computing module 400 or to communicate externally.

Computing module 400 might also include one or more memory modules,simply referred to herein as main memory 408. For example, random accessmemory (RAM) or other dynamic memory might be used for storinginformation and instructions to be executed by processor 404. Mainmemory 408 might also be used for storing temporary variables or otherintermediate information during execution of instructions to be executedby processor 404. Computing module 400 might likewise include a readonly memory (“ROM”) or other static storage device coupled to bus 402for storing static information and instructions for processor 404. Thecomputing module 400 might also include one or more various storagedevices 410, which might include, for example, a magnetic tape drive, anoptical disc drive, a solid state drive, removable storage media such asa CD/DVD, Compact-Flash memory, SD memory, or any other non-volatilememory.

Computing module 400 might also include a communications interface 420.Communications interface 420 might be used to allow software and data tobe transferred between computing module 400 and external devices.Examples of communications interface 420 might include a modem orsoftmodem, a network interface (such as an Ethernet, network interfacecard, WiMedia, IEEE 802.XX, 3G or 4G LTE cellular network interface, orother interface), a communications port (such as for example, a USBport, IR port, RS232 port Bluetooth® interface, or other port), or othercommunications interface. Software and data transferred viacommunications interface 420 might typically be carried on signals,which can be electronic, electromagnetic (which includes optical) orother signals capable of being exchanged by a given communicationsinterface 420. These signals might be provided to communicationsinterface 420 via a channel 425. This channel 425 might carry signalsand might be implemented using a wired or wireless communication medium.Some examples of a channel might include a phone line, a cellular link,an RF link, an optical link, a network interface, a local or wide areanetwork, and other wired or wireless communications channels.

Computing module 400 might also include one or more user inputs 430. Theuser input allows for the user to enter commands to the computing module400 and interact with it. Examples of user inputs might include acomputer mouse, a keyboard, a touch-sensitive screen, a stylus, amousepad, a joystick, an accelerometer, a gyroscope, a camera, a remotecontrol, or any other user input mechanism.

The computer module 400 might also include one or more user outputinterfaces 440. The user output interfaces 440 might be used to interactwith the user by presenting information or sensory outputs for the user.Examples of user output interfaces might include visual outputs, such asa display screen or monitor, or audio outputs, such as a speaker orheadphone output.

In this document, the terms “computer readable medium” and “computerusable medium” are used to generally refer to media such as, forexample, memory 408, storage unit 410, and channel 425. These and othervarious forms of computer readable media or computer usable media may beinvolved in carrying one or more sequences of one or more instructionsto a processing device for execution. Such instructions embodied on themedium, are generally referred to as “computer program code” or a“computer program product” (which may be grouped in the form of computerprograms or other groupings). When executed, such instructions mightenable the computing module 400 to perform features or functions of thepresent disclosure as discussed herein.

While various embodiments of the present disclosure have been describedabove, it should be understood that they have been presented by way ofexample only, and not of limitation. Likewise, the various diagrams maydepict an example architectural or other configuration for thedisclosure, which is done to aid in understanding the features andfunctionality that can be included. The disclosure is not restricted tothe illustrated example architectures or configurations, but the desiredfeatures can be implemented using a variety of alternative architecturesand configurations. Indeed, it will be apparent to one of skill in theart how alternative functional, logical or physical partitioning andconfigurations can be implemented to implement the desired features.Additionally, with regard to flow diagrams, operational descriptions andmethod claims, the order in which the steps are presented herein shallnot mandate that various embodiments be implemented to perform therecited functionality in the same order unless the context dictatesotherwise. Thus, the breadth and scope of the present disclosure shouldnot be limited by any of the exemplary embodiments.

Terms and phrases used in this document, and variations thereof, unlessotherwise expressly stated, should be construed as open ended as opposedto limiting. As examples of the foregoing: the term “including” shouldbe read as meaning “including, without limitation” or the like; the term“example” is used to provide exemplary instances of the item indiscussion, not an exhaustive or limiting list thereof; the terms “a” or“an” should be read as meaning “at least one,” “one or more” or thelike; and adjectives such as “conventional,” “traditional,” “normal,”“standard,” “known” and terms of similar meaning should not be construedas limiting the item described to a given time period or to an itemavailable as of a given time, but instead should be read to encompassconventional, traditional, normal, or standard technologies that may beavailable or known now or at any time in the future. Likewise, wherethis document refers to technologies that would be apparent or known toone of ordinary skill in the art, such technologies encompass thoseapparent or known to the skilled artisan now or at any time in thefuture.

Although the disclosure has been presented with reference only to thepresently preferred embodiments, those of ordinary skill in the art willappreciate that various modifications can be made without departing fromthis disclosure. As such, the disclosure is defined only by thefollowing claims and recited limitations.

1. An authentication server, comprising: a hardware processor; and anon-transitory machine-readable storage medium encoded with instructionsexecutable by the hardware processor to perform a method ofauthenticating images received from a client device, the methodcomprising: receiving, by the authentication server, an image file fromthe client device via a network, obtaining, by the authenticationserver, first geolocation information from an image authenticationapplication executing at the client device and in communication with theauthentication server, wherein the first geolocation informationcomprises information obtained by the image authentication applicationthat indicates a first geolocation at which the image authenticationapplication was opened on the client device, obtaining, by theauthentication server, second geolocation information from the imageauthentication application, wherein the second geolocation informationcomprises information obtained by the image authentication applicationthat indicates a second geolocation at which the request to transmit theimage file to the authentication server was received by theauthentication application, determining, by the authentication server,one or more geographic requirements have been satisfied, wherein the oneor more geographic requirements includes a requirement that the secondlocation is within a predefined distance from the first location, andgenerating, by the authentication server, an authenticated image filebased on the image file and the authentication information responsive tothe determination that the one or more geographic requirements have beenmet.
 2. The authentication server of claim 1, the method furthercomprising: applying, by the authentication server, date and timeinformation to the tagged image; creating, by the authentication server,a resource location identifier associated with the image file, theresource location identifier identifying a file location; uploading, bythe authentication server, the photographic image, the tagged image, orboth to the file location identified by the resource locationidentifier; and transmitting, by the authentication server, anauthenticated image file to the client device, the authenticated imagefile comprising one or more of: the tagged image, the image, the dateand time information, and the resource location identifier.
 3. Theauthentication server of claim 1, the method further comprising:receiving, by the authentication server, metadata associated with theimage; and using, by the authentication server, the metadata to verifythat one or more timing requirements have been satisfied.
 4. Theauthentication server of claim 3, wherein: the one or more timingrequirements comprises a requirement that the image file was received atthe authentication server within a predetermined time frame after theimage authentication application was opened on the client device.
 5. Theauthentication server of claim 3, wherein: the one or more timingrequirements comprises a requirement that the image authenticationapplication received a request to transmit the image file to theauthentication server within a predetermined time frame after the imagewas captured by the image authentication application.
 6. Theauthentication server of claim 3, wherein: the one or more timingrequirements comprises a requirement that the image authenticationapplication received a request to transmit the image file to theauthentication server within a predetermined time frame after the imageauthentication application was opened on the client device.
 7. Theauthentication server of claim 1, the method further comprising:applying, by the authentication server, an authenticity indicator to theimage to create a tagged image, wherein the authenticity indicatorcomprises a visual watermark applied to the image.
 8. A non-transitorymachine-readable storage medium encoded with instructions executable bya hardware processor of an authentication server, the machine-readablestorage medium comprising instructions to cause the hardware processorto perform a method of authenticating images received from a clientdevice, the method comprising: receiving, by the authentication server,an image file from the client device via a network; obtaining, by theauthentication server, first geolocation information from an imageauthentication application executing at the client device and incommunication with the authentication server, wherein the firstgeolocation information comprises information obtained by the imageauthentication application that indicates a first geolocation at whichthe image authentication application was opened on the client device;obtaining, by the authentication server, second geolocation informationfrom the image authentication application, wherein the secondgeolocation information comprises information obtained by the imageauthentication application that indicates a second geolocation at whichthe request to transmit the image file to the authentication server wasreceived by the authentication application; determining, by theauthentication server, one or more geographic requirements have beensatisfied, wherein the one or more geographic requirements includes arequirement that the second location is within a predefined distancefrom the first location; and generating, by the authentication server,an authenticated image file based on the image file and theauthentication information responsive to the determination that the oneor more geographic requirements have been met.
 9. The non-transitorymachine-readable storage medium of claim 8, the method furthercomprising: applying, by the authentication server, date and timeinformation to the tagged image; creating, by the authentication server,a resource location identifier associated with the image file, theresource location identifier identifying a file location; uploading, bythe authentication server, the photographic image, the tagged image, orboth to the file location identified by the resource locationidentifier; and transmitting, by the authentication server, anauthenticated image file to the client device, the authenticated imagefile comprising one or more of: the tagged image, the image, the dateand time information, and the resource location identifier.
 10. Thenon-transitory machine-readable storage medium of claim 8, the methodfurther comprising: receiving, by the authentication server, metadataassociated with the image; and using, by the authentication server, themetadata to verify that one or more timing requirements have beensatisfied.
 11. The non-transitory machine-readable storage medium ofclaim 10, wherein: the one or more timing requirements comprises arequirement that the image file was received at the authenticationserver within a predetermined time frame after the image authenticationapplication was opened on the client device.
 12. The non-transitorymachine-readable storage medium of claim 10, wherein: the one or moretiming requirements comprises a requirement that the imageauthentication application received a request to transmit the image fileto the authentication server within a predetermined time frame after theimage was captured by the image authentication application.
 13. Thenon-transitory machine-readable storage medium of claim 10, wherein: theone or more timing requirements comprises a requirement that the imageauthentication application received a request to transmit the image fileto the authentication server within a predetermined time frame after theimage authentication application was opened on the client device. 14.The non-transitory machine-readable storage medium of claim 8, themethod further comprising: applying, by the authentication server, anauthenticity indicator to the image to create a tagged image, whereinthe authenticity indicator comprises a visual watermark applied to theimage.
 15. A method of authenticating images received from a clientdevice, the method being implemented by an authentication server havingone or more processors programmed to perform the method, the methodcomprising: receiving, by the authentication server, an image file fromthe client device via a network; obtaining, by the authenticationserver, first geolocation information from an image authenticationapplication executing at the client device and in communication with theauthentication server, wherein the first geolocation informationcomprises information obtained by the image authentication applicationthat indicates a first geolocation at which the image authenticationapplication was opened on the client device; obtaining, by theauthentication server, second geolocation information from the imageauthentication application, wherein the second geolocation informationcomprises information obtained by the image authentication applicationthat indicates a second geolocation at which the request to transmit theimage file to the authentication server was received by theauthentication application; determining, by the authentication server,one or more geographic requirements have been satisfied, wherein the oneor more geographic requirements includes a requirement that the secondlocation is within a predefined distance from the first location; andgenerating, by the authentication server, an authenticated image filebased on the image file and the authentication information responsive tothe determination that the one or more geographic requirements have beenmet.
 16. The method of claim 15, further comprising: applying, by theauthentication server, date and time information to the tagged image;creating, by the authentication server, a resource location identifierassociated with the image file, the resource location identifieridentifying a file location; uploading, by the authentication server,the photographic image, the tagged image, or both to the file locationidentified by the resource location identifier; and transmitting, by theauthentication server, an authenticated image file to the client device,the authenticated image file comprising one or more of: the taggedimage, the image, the date and time information, and the resourcelocation identifier.
 17. The method of claim 15, further comprising:receiving, by the authentication server, metadata associated with theimage; and using, by the authentication server, the metadata to verifythat one or more timing requirements have been satisfied.
 18. The methodof claim 17, wherein: the one or more timing requirements comprises arequirement that the image file was received at the authenticationserver within a predetermined time frame after the image authenticationapplication was opened on the client device.
 19. The method of claim 17,wherein: the one or more timing requirements comprises a requirementthat the image authentication application received a request to transmitthe image file to the authentication server within a predetermined timeframe after the image was captured by the image authenticationapplication.
 20. The method of claim 17, wherein: the one or more timingrequirements comprises a requirement that the image authenticationapplication received a request to transmit the image file to theauthentication server within a predetermined time frame after the imageauthentication application was opened on the client device.